[draft] Stats UI improvements - #186
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Note the comment in As I just spent a lot of time rewriting this I am not really a fan of having it all immediately removed, but I haven't yet seen what it looks like. Include some screenshots please. I also worry XAML will be harmful to the performance, for example I'm guessing it has more expensive alpha blending, but maybe you can compare the performance hit. I think XAML would be nice to ditch altogether when streaming, it's unknown yet if being in a SwapChainPanel is the source of some problems with VRR. Not sure Logs needs any features, but one change I would make is to shorten the list of resolution text so it fits on one line: |
…outing a lot more flexible and removes complexity from DX rendering
d013e43 to
d308350
Compare
|



I moved the stats into the XAML layer so it's easier to layout for readability and added a semi-transparent black backbox so stats can actually be read (this is also more in-line with what the original Moonlight project does).
This PR is a work in progress.
ToDo: